-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixes-#6198-vsphere-provider-improve-documentation #6200
fixes-#6198-vsphere-provider-improve-documentation #6200
Conversation
domain = "${var.vsphere_domain}" | ||
datacenter = "${var.vsphere_datacenter}" | ||
cluster = "${var.vsphere_cluster}" | ||
resource_pool = "${var.vsphere_cluster}/Resources/${var.vsphere_resource_pool}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AWESOME!! How about some english describing how this works?? How about when there is not a cluster? Any other use cases?
@tommymalmqvist any comments on my nit picks? |
hey @chrislovecnm, I have moved the info. Check and see what you think. 👍 |
e0fe2df
to
0108ef7
Compare
Thanks @tommymalmqvist! |
@stack72 thanks - but what u doin working on a Sunday :P Animal!! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
There is some confusion about using the resource_pool arument to the resource definition. This will add a more complete example.
issue 6198
#6198